|
In the United States military integrated acquisition lifecycle〔(Integrated Defense AT&L Lifecycle Management Chart )〕 the Technical section has multiple acquisition "Technical Reviews".〔(Technical Review Definitions )〕 Technical reviews and audits assist the acquisition and the number and types are tailored to the acquisition.〔(Systems Engineering Technical Reviews slider )〕 Overall guidance flows from the Defense Acquisition Guidebook chapter 4,〔(Defense Acquisition Guidebook )〕 with local details further defined by the review organizations.〔(NAVSEA Technical Review Manual )〕〔(【引用サイトリンク】 NAVAIR INST 4355.19D, Systems Engineering Technical Review Process )〕〔(【引用サイトリンク】 Everyspec NAVAIRINST 4355.19 Systems Engineering Technical Review (incl supplement B) )〕〔(''Systems Engineering Fundamentals.'' ), Ch. 11 Technical Reviews and Audits; App 16-a Schedules Defense Acquisition University Press, 2001〕 Typical topics examined include adequacy of program/contract metrics, proper staffing, risks, budget, and schedule. In NASA's engineering design life cycle, a phase of design reviews are held for technical and programmatic accountability and to authorize the release of funding to a project.〔NASA Procedural Requirements, (Subject: NASA Systems Engineering Processes and Requirements, Appendix G ) Responsible Office: Office of the Chief Engineer, NPR 7123.1B, Effective Date: April 18, 2013, Expiration Date: April 18, 2018〕 This article describes the major phases of that systems engineering process. A design review provides an in-depth assessment, by an independent team of discipline experts and managers, that the design (or concept) is realistic and attainable from a programmatic and technical sense. Design review is also required of medical device developers as part of a system of design controls described in the US Food and Drug Administration's governing regulations in 21CFR820. In 21CFR820.3(h), design review is described as " documented, comprehensive, systematic examination of the design to evaluate the adequacy of the design requirements, to evaluate the capability of the design to meet these requirements, and to identify problems." The FDA also specifies that a design review should include an independent reviewer. == Review process == The list of reviews done by an effort and the content, nature, process, and objectives any review uses vary enormously by the organization involved and the particular situation of the effort. For example, even within the U.S. Department of Defense, System Requirements Review cases include such as (1) a 5-day perusal of each individual requirement, or (2) a 2-day discussion of development plan documents allowed only after the system requirements have been approved and the development documents reviewed with formal action items required, or (3) a half-day powerpoint with content determined by the Project Manager with attendance limited to high-level (non-technical) stakeholders with no output other than the PM being able to claim 'SRR done'. Some of the reviews that may be done on an effort include: 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Design review (U.S. government)」の詳細全文を読む スポンサード リンク
|